<?php
/**
 * <https://y.st./>
 * Copyright © 2018 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Recipe finished',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2018/06/02.jpg" alt="A pink, flowering dogwood tree" class="framed-centred-image" width="649" height="480"/>
<section id="recipe">
	<h2>Dill pickle ranch</h2>
	<p>
		This time, I substituted both the vinegar and the soy milk in my <a href="/en/recipe/ranch_dressing.xhtml">ranch dressing recipe</a> with pickle juice.
		I also left out the added salt, seeing as pickle juice is already so salty.
		I&apos;d already seen that substituting just the vinegar out wasn&apos;t enough.
		I figured I&apos;d need less soy milk and more pickle juice, but I still thought I&apos;d need <strong>*some*</strong> soy milk.
		My intention with this batch was to go to the extreme side of the pickle juice use spectrum so I could compare it to my last batch and quickly gage about how much juice and milk I should use in my next real attempt.
		Instead, I found that the pickle flavour is <strong>*still*</strong> weaker than I&apos;d like it to be and, even more surprisingly, the dressing is still opaque and white.
		I thought for sure with that much juice, it&apos;d overwhelm the mayo enough to add a slight transparency.
	</p>
	<p>
		Anyway, unless I want to boil down the pickle juice to concentrate it, this is the end of the line.
		The problem with boiling it down is that I&apos;ve got to do it in a repeatable way to get a consistent result, seeing as I&apos;m building a recipe.
		I have to be able to convey exactly how much to boil out, and I&apos;m not even sure how to measure or repeat such a boil-down procedure.
		Besides, I&apos;m not sure it&apos;s worth the effort.
		This pickle ranch isn&apos;t as strong as I&apos;d like it to be, but it&apos;s still good, so I&apos;m releasing the <a href="/y.st./source/y.st./source/pages/en/recipe/dill_pickle_ranch_dressing.xhtml">recipe for dill pickle ranch</a> as-is.
	</p>
	<p>
		I&apos;m a fatso.
		I really need to stop eating all this ranch, even if it does mean I get a lot of leafy greens.
		I think I want to try making a different dressing.
		Specifically, I&apos;d like to try to imitate whatever dressing was on that Reuben from the other day.
		Thousand island, I think?
		Something like that.
		The best part is that now I&apos;m aware that recipes aren&apos;t subject to copyright law.
		I don&apos;t have to avoid using recipes I find online to construct my own.
		In fact, if I find a good enough recipe, I don&apos;t even need to modify it; I can just link to it.
	</p>
</section>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		One of my professors asked the class if anyone has downloaded their Gmail archive in mbox format, and if so, using what client and operating system.
		Gmail?
		Seriously?
		Like, I understand many people use Gmail.
		But why ask specifically about Gmail and not email accounts in general?
		The mbox format isn&apos;t specific to Gmail in any way.
		My response:
	</p>
	<blockquote>
		<p>
			I don&apos;t use Gmail, myself.
			Using Gmail requires a Google account.
			Google doesn&apos;t allow the creation of accounts unless the user provides their telephone number, which Google then verifies before allowing the account to be created.
			First of all, that&apos;s incredibly creepy.
			No doubt, it&apos;s just Google trying to mine even more information to use in selling us to their advertisers.
			(With Google, you&apos;re not the customer, which is why you don&apos;t pay anything; you&apos;re the <strong>*product*</strong>.
			Advertisers are the customers.)
			But also, I don&apos;t even have telephone service.
			Google necessarily excludes those of us that don&apos;t have telephone service in their effort to make sure that all their users that do have it don&apos;t refuse to provide Google with the telephone number information Google covets.
		</p>
		<p>
			I do use Thunderbird though, on Debian.
			Once the term ends, I plan to migrate most of my workflow onto my new PureOS (a fork of Debian; Debian has so, so many forks) machine, where I&apos;ll probably continue using Thunderbird.
			I&apos;m not sure what format I have Thunderbird set to download in or how to change it; it might be using mbox format.
			I do download all the emails I&apos;ve processed though, or at least the ones I don&apos;t delete.
			It clears space on the server so I don&apos;t have to worry about my account space overfilling and missing an email.
		</p>
	</blockquote>
	<p>
		My discussion post for the day:
	</p>
	<blockquote>
		<p>
			Like you said, the the $a[POP3] client must conform to the standard format used for <strong>*Internet exchange*</strong>.
			That means that, on the wire, the emails need to be in the standard format and both client and server need to use said format.
			However, what about on disk?
			$a[POP3] isn&apos;t used for disk storage, only for Internet exchange.
			So what prevents different $a[POP3] servers from having emails stored on disk in different formats?
		</p>
	</blockquote>
</section>
END
);
